home *** CD-ROM | disk | FTP | other *** search
- I, perhaps more than anyone else, want to put a lid on further IMAP additions
- in the name of stability and getting a Proposed Standard out of this.
- However, something has come out that has survived even my harsh filters, and
- I'm throwing it out to the list to be blessed (or damned, as the case may be).
-
- The proposed change is a new form of FETCH which allows the selecting fetching
- of message headers. The problem to be solved is that RFC-822 certain header
- lines are not represented in the IMAP envelope structure, nor is there any
- reasonable way to extend the envelope structure to accomodate them. It is
- considered mandatory that any extension be upwards/downwards compatible and
- not require revisiting the next time we need to be able to snarf another
- header.
-
- The most obvious example is the ReSent-Date/ReSent-From/ReSent-To header
- lines. There is an additional problem with these particular header lines in
- that they can not be arbitrarily reordered and retain the same meaning.
-
- Other headers, such as Newsgroups:, are also perceived as interesting.
-
- The proposed two new functions are a ``fetch all header lines of this message
- whose field names match any in this list'' and ``fetch all header lines of
- this message whose names do not match any in this list''. They take an
- argument which consists of a list of the field names. The result of these
- functions is a text string similar to that from RFC822.HEADER. All header
- lines are returned in the original order of the message (note this is a
- requirement for useful ReSent information).
-
- For example (note that line breaks are here only for clarity):
-
- A001 FETCH 23:30 (ENVELOPE RFC822.HEADER.LINES ("Resent-Date" "Resent-From"
- "Resent-To")
-
- would fetch the envelopes and remail information for messages 23 to 30.
-
- A001 FETCH 23 RFC822.HEADER.LINES.NOT ("Return-Path" "Received")
-
- would fetch the header of message 23 without the ``Return-Path'' or
- ``Received'' header lines.
-
- This would become a fundamental API call in c-client, and c-client would
- simulate its results if it finds itself talking to an IMAP server that does
- not support it.
-
- Comments please.
-
-
-
-